Systems and methods employing delimiter searches to identify sensitive information in data

ABSTRACT

A data string that includes potentially sensitive information, such as an account number for a payment card, may be evaluated using a delimiter search to provide an increased level of confidence that the data string encodes the sensitive information of interest. A delimiter search may include an evaluation of the bytes adjacent to the beginning and end of the data to determine whether or not those bytes have values that correspond to the values of known delimiters. A data string that is not surrounded by known delimiters may be disregarded (i.e., considered not to comprise sensitive information of interest), while a data string that is surrounded by known delimiters may warrant further evaluation.

CROSS-REFERENCE TO RELATED APPLICATION

A claim for priority under 35 U.S.C. §119(e) is made to the May 28, 2010, filing date of U.S. Provisional Patent Application 61/349,809, titled “SYSTEMS FOR DETERMINING WHETHER BATCHES OF DATA INCLUDE STRINGS THAT CORRESPOND TO SENSITIVE INFORMATION,” the entire disclosure of which is, by this reference, hereby incorporated herein.

TECHNICAL FIELD

The present invention relates generally to methods and systems for scanning systems that collect and disseminate sensitive information (e.g., merchants' systems that process transactions with payment cards, etc.) and, more specifically, to methods and systems for recognizing sensitive information (e.g., payment card account numbers, etc.) in large groups of data.

BACKGROUND OF RELATED ART

Credit card and debit card, or “payment card,” processing involves a number of parties, including a card association, an issuer, a cardholder, an acquirer, and a merchant.

When a potential cardholder, such as an individual or an organization, wants a payment card, they approach an issuer. The issuer is a financial institution. If the potential cardholder meets certain requirements (e.g., credit rating, account balance, income, etc.), the issuer may choose to issue a payment card to the cardholder. The payment card contains sensitive information about the cardholder, including the cardholder's identity and account information, which enables the cardholder to transfer funds from an account held by the issuer or to draw against a corresponding line of credit provided by the issuer.

A cardholder makes a purchase, or initiates a transaction, with the payment card by presenting the same to a merchant. Information obtained from the payment card by the merchant is then processed. The information may be processed using equipment that may be provided by an acquirer, which is a financial institution with which the merchant has an established relationship. As the information is processed, it is transferred to a card association (e.g., VISA, MASTERCARD, etc.), either directly from the merchant or through the acquirer. The card association transmits the information about the transaction to the issuer. The issuer then authorizes or declines the transaction. If the transaction is authorized, the issuer funds the transaction by transferring money to the acquirer through the card association. When a debit card is used, funds are transferred from the cardholder's account with the issuer to the acquirer. When the cardholder uses a credit card, the cardholder incurs a debt with the issuer, for which the cardholder must eventually reimburse the issuer.

Whenever a cardholder uses a payment card to make a purchase, the merchant obtains information, including the account number, from the payment card. While that information may be obtained in a number of ways, the merchant typically uses some type of electronic processing equipment to transmit the information, by way of a communication element (e.g., an Internet connection, etc.) to its acquirer or a card association. Sometimes the information is stored in memory associated with the processing equipment. That information may be stored in groups that include long strings of data.

Since the processing equipment includes a communication element, any memory associated with the processing equipment may be subject to hacking. Thus, any information stored in memory associated with processing equipment may be subject to theft. When payment card information is stolen, that information may be used to make unauthorized purchases.

DISCLOSURE

The present invention includes methods and systems for identifying sensitive information (e.g., payment card information, etc.) in large groups of data that have been stored in memory associated with collection systems (e.g., equipment for processing payment card transactions, etc.).

In one aspect, a method of the present invention includes various embodiments of methods and systems for identifying potentially sensitive information (e.g., account numbers for payment cards, etc.). In one embodiment, strings of consecutive bytes with values that correspond to characters of interest (e.g., decimal numerals or numeric digits (i.e., a character having a value that corresponds to a base-ten, or Arabic, numeral), etc.) and with lengths that correspond to a length of sensitive information of interest (e.g., a payment card account number, etc.) are identified as including potentially sensitive information. Such a string of bytes may be referred to as a “tagged string.”

Once a tagged string has been identified, the tagged string may be further evaluated to provide an increased level of confidence that the bytes of the tagged string correspond to characters of potentially sensitive information of interest. Any tagged strings that are unlikely to include the potentially sensitive information of interest may be disregarded. In some embodiments, the further evaluation comprises a much less intensive process and, thus, less time to complete, than a final process for verifying whether a tagged string actually includes sensitive information of interest. Thus, quicker processes may be used to disregard, or weed out, the majority of data within a group, while the more intensive final process may be reserved for data strings that are likely to include the sensitive information of interest.

In one embodiment, further evaluation of a tagged string that includes potentially sensitive information may comprise a delimiter search. A delimiter search may include an evaluation of the bytes adjacent to the beginning and end of the string of bytes that correspond to a tagged string of data. In various embodiments, a delimiter search includes evaluation of the adjacent bytes to determine whether or not they encode values that correspond to the values of known delimiters (e.g., a comma (,), a tab ( ), a space ( ), a slash (/or \), etc.). Characters that are typically used in numeric sequences (e.g., a dash (-), a period (.), etc.) and strings (e.g., two or more sequential bytes, etc.) of alphabetic characters (e.g., names, etc.) may, in some embodiments, be considered not to comprise delimiters. A tagged string that is not surrounded by known delimiters may be disregarded (i.e., considered not to comprise sensitive information), while a tagged string that is surrounded by known delimiters may warrant further evaluation.

Searching and/or evaluation may be “ordinal” (e.g., one byte searching, then two byte searching (both little endian (LE) and big endian (BE)), then four byte searching (both LE and BE), etc.) to enable the search algorithm to identify data of interest across a plurality of Unicode Transformation Formats (UTFs), or regardless of the particular type of UTF, in which the data may be encoded (e.g., UTF-8, UTF-16LE, UTF-16BE, UTF-32LE, UTF-32BE).

A tagged string that includes potentially sensitive information (e.g., an account number for a payment card, etc.) may also be evaluated to determine whether or not the tagged string includes a known identifier that typically accompanies a particular type of sensitive information (e.g., a bank identification number (BIN) of a payment card account number, etc). A search for a known identifier may be effected using a so-called “trie” algorithm.

A tagged string comprising potentially sensitive information that has at least been subjected to a delimiter search in accordance with teachings of the present invention may then be subjected to a verification process. In some embodiments, known processes may be used to determine whether or not a tagged string includes sensitive information (e.g., an account number for a payment card, etc.). In a specific embodiment, a known validation or “checksum” algorithm, such as the Luhn algorithm, may be used to determine whether or not a tagged string actually encodes a payment card account number.

A system of the present invention may execute one or more of the processes that have been described above. The above-described processes may be implemented in the form of a program that may be executed by a processing element (e.g., computer processor, etc.) that evaluates, or scans, stored data. The data may be stored in memory associated with the processing element or in memory of a separate electronic device. The processing element may access the stored data by way of a suitable communication element, such as circuitry and/or wiring within the same electronic device (e.g., computer, etc.) as the processing element, a wired communication link between the electronic device of which the processing element is a part and a separate electronic device of which the memory is a part, or remotely (e.g., over an Internet connection, etc.).

Other aspects, as well as features and advantages of various aspects, of the present invention will become apparent to those of ordinary skill in the art through consideration of the ensuing description, the accompanying drawings, and the appended claims.

BRIEF DESCRIPTION OF THE DRAWINGS

In the drawings:

FIG. 1 is a schematic representation of an embodiment of an evaluation system of the present invention, which includes a collection system and a scanning device for evaluating the collection system;

FIG. 2 is a diagram that illustrates an embodiment of a network in which sensitive information, such as account information corresponding to payment cards, may be collected and disseminated, and in which searches for sensitive information may be conducted;

FIG. 3 is a flow chart that illustrates an embodiment of a process by which data is evaluated to determine whether any sensitive information of interest has been stored therein; and

The flow chart of FIG. 4 and the schematic representation of FIG. 4A illustrate an embodiment of a delimiter search, in which bytes surrounding a tagged string are analyzed to determine if their values correspond to the values of known delimiters.

DETAILED DESCRIPTION

The present invention includes various embodiments of systems for evaluating data to determine whether or not the data includes potentially sensitive information. FIG. 1 schematically depicts an embodiment of such an evaluation system 10, in which an electronic device, referred to here is a “scanning device 20,” is configured to communicate with and scan data stored by a component of another electronic device that collects sensitive information, which is referred to herein as a “collection system 40.”

The collection system 40 includes a memory device (e.g., a hard drive, etc.), or “memory 42” for the sake of simplicity, that stores data 44, which potentially includes sensitive information. In addition to memory 42, a collection system 40 of an evaluation system 10 of the present invention may include or be associated with a processing element 46, such as a microprocessor, a microcontroller, or the like.

The scanning device 20 is programmed to determine whether the data 44 stored by the memory 42 of the collection system 40 includes any potentially sensitive information. Programming of the scanning device 20, which may be in the form of software or firmware, controls operation of a processing element 22 of the scanning device 20. Some embodiments of processing elements 22 that may be included in a scanning device 20 of an evaluation system 10 of the present invention include, without limitation, microprocessors, microcontrollers, and elements that may be configured to execute a particular program. In embodiments where a scanning device 20 of an evaluation system 10 of the present invention is configured for direct connection to a collection system 40, the scanning device may be portable (e.g., a laptop computer; a hand-held computer, such as a so-called “smart phone,” etc.; a dedicated scanner; etc.). In embodiments where a scanning device 20 is configured to remotely scan one or more collection systems 40, the scanning device 20 may comprise a server, or a device (e.g., a dedicated scanning device, a smart phone, etc.) that may connect remotely to the collection system 40 (e.g., through a cellular telephone data connection, etc.).

Communication between the memory 42 of the collection system 40 and a processing element 22 of the scanning device 20 may be established in any suitable manner known in the art. In embodiments where both the scanning device 20 and the collection system 40 comprise electronic devices, a communication link between the scanning device 20 and the collection system 40 may be direct or indirect. A direct connection may include a physical, or “wired,” coupling between the scanning device 20 and the collection system, or it may include a close proximity wireless connection (e.g., a Bluetooth connection, a wireless local area network (WLAN) (e.g., a WiFi network operating in accordance with an IEEE 802.11 standard, etc.). An indirect connection may be established more remotely (e.g., over the Internet, etc.). In some embodiments where an indirect connection is established between the scanning device 20 and the collection system 40, the scanning device 20 of an evaluation system 10 that incorporates teachings of the present invention may be located at a central location, and may be configured to selectively communicate with a plurality of different collection systems 40 at a plurality of different locations.

An evaluation system 10 may be used in a variety of contexts or environments where sensitive information (e.g., account numbers, usernames and associated passwords, Social Security numbers or similar identifiers, etc.) is used. In a specific embodiment, the evaluation system 10 is configured to scan for and identify potential credit card numbers and debit card numbers, which are collectively referred to herein as “payment card numbers.” The scanning device 20 in such an embodiment may comprise a server under control of an approved scanning vendor (ASV), which is a party that has been authorized to access and evaluate the systems (i.e., the collection systems 40, such as card readers, associated computers, etc.) employed by one or more merchants to acquire information from a consumer's payment card.

The relationships between the various parties that may be involved in payment card transactions are illustrated by the schematic representation of FIG. 2. More specifically, FIG. 2 depicts a network 100 that includes a card association 110; an issuer 120; a cardholder, or consumer 130; a merchant 140; and an acquirer 150.

The card association 110 is generally recognized as the entity whose identity appears most prominently on a payment card 132. Examples of card associations 110 include, but are certainly not limited to, Visa, Master Card, American Express, and Discover. As depicted, the card association 110 may act as a gateway between an issuer 120 and an acquirer 170, enabling the authorization and funding of a consumer 130's transactions. In some embodiments, a card association 110 (e.g., American Express, Discover, etc.) may also serve as the issuer 120, as depicted by box 150 in FIG. 2.

The issuer 120 may be a financial institution. As FIG. 2 schematically represents, there is a direct relationship between the issuer 120 and each of its consumers 130: the issuer 120 provides each of its consumers 130 with a payment card 132. In so doing, the issuer 120 may determine whether or not each of its consumers 130 meets certain qualifications, such as credit history, income or revenue, available funds, employment status, and other indicators of the ability of a particular consumer 130 to pay for transactions that will be enabled by use of the payment card 132.

The consumer 130 may be an individual, a business, or any other entity. Each consumer 130 should assume responsibility for its payment card 132, as well as the information on or otherwise associated with the payment card 132.

Each merchant 140 is a party that provides goods or services to a variety of consumers 130. In the network 100, a merchant 140 provides consumers 130 with the option to use payment cards 132 to complete transactions for the merchant 140's goods or services. When a consumer 130 chooses to use a payment card 132 to complete a transaction, the merchant 140 uses a collection system 40 (FIG. 1) to obtain account information 134 (e.g., an account number, an expiration date, information about the consumer 130's identity, etc.) from the payment card 132. That account information 134 is then transmitted, along with information about the transaction, or “transaction information 136,” by the collection system 40 to the card association 110. The transaction information 136 may include data indicative of the point of sale, the date and time of the transaction, goods or services purchased as part of the transaction, the monetary amount of the transaction, and the like.

The account information 134 and the corresponding transaction information 136 may be transmitted to the card association 110 either directly or through the acquirer 150, which is a financial institution (e.g., a bank, etc.) with which the merchant 140 has an established relationship.

The card association 110 then transmits the account information 134 and the corresponding transaction information 136 to the issuer 120, which authorizes or declines the transaction. If the transaction is authorized, the issuer 120 funds the transaction. Where an acquirer 150 is involved, the issuer 120 transfers money 138 to the acquirer 150 through the card association 110. When the payment card 132 is a debit card, funds are transferred from the cardholder's account with the issuer 120 to the acquirer 150. When the consumer 130 uses a credit card, the consumer 130 incurs a debt with the issuer 120, for which the consumer 130 must eventually reimburse the issuer 120.

The Payment Card Industry (PCI), an organization that governs the network 100, sets standards for the collection, storage, and transmission of account information 134 within the network 100. These standards are known as PCI's Data Security Standards (DSS). In view of the ever-increasing danger that sensitive account information 134 will be stolen, the PCI often modifies, typically increasing, the DSS.

Each merchant 140 within the network 100 (i.e., each merchant 140 that accepts payment cards 132 from its consumers 130) must comply with the current version of the DSS or risk exorbitant fines from PCI. In addition, a merchant 140 that does not comply with the current DSS may be liable to its consumers 130 for the misappropriation of their sensitive account information 134.

In order to ensure that the merchants 140 within the network 100 comply with the current DSS, the network 100 may also include one or more approved scanning vendors 160 (ASVs). An ASV 160 is an entity that has been certified by PCI to evaluate the systems (e.g., collection systems 40) that are used within the network 100 to collect and transmit account information 134, and to determine whether or not those systems are DSS compliant. Each ASV 160 may be employed by one or more merchants 140, by one or more acquirers 150, or by a card association 110.

With returned reference to FIG. 1, an ASV 160 (FIG. 2) may use a scanning device 20 to verify whether or not a merchant's collection systems 40 are DSS compliant. Communication may be established between the processing element 22 of the scanning device 20 and various components of a merchant 140's collection system 40, including, but not limited to, its memory 42. Communication between the processing element 22 and the collection system 40 may be direct or remote, and may be established by any suitable technique or protocol.

In determining whether or not a merchant's collection system 40 is DSS compliant, the processing element 22 of the ASV 160's (FIG. 2) scanning device 20 operates under control of one or more programs (e.g., computer programs, etc.) to evaluate certain aspects of the collection system 40. Various embodiments of programs that control operation of the processing element 22, as well as the processes that are effected by such programs in accordance with teachings of the present invention, are described hereinafter.

In a specific embodiment, a process or program of the present invention may cause the processing element 22 of a scanning device 20 to evaluate data 44 stored by one or more components (e.g., memory 42, etc.) of a merchant 140's (FIG. 2) collection system 40 to determine whether the data 44 includes account information 134 that corresponds to one or more payment cards 132 (FIG. 2). More specifically, a program of the present invention may be configured to effect a process in which data 44 is evaluated to determine whether it includes any data strings that are likely to comprise payment card account numbers. Such a process 200 is illustrated by the diagram of FIG. 3.

In FIG. 3, at reference 210, data 44 stored by memory 42 associated with a merchant's collection system 40 (FIG. 1) is evaluated. Specifically, the data 44 is evaluated to determine whether or not it includes any strings of data that might comprise sensitive information, such as a payment card account number or the like. Without limiting the scope of the present invention, a payment card account number may be thirteen (13) to sixteen (16) digits long. In memory 42, or the data 44, a payment card account number may comprise a number of consecutive bytes (e.g., thirteen (13) to sixteen (16) in UTF-8 (8-bit Unicode Transformation Format) encoding, twenty-six (26) to thirty-two (32) in UTF-16 (16-bit Unicode Transformation Format) encoding, fifty-two (52) to sixty-four (64) in UTF-32 (32-bit Unicode Transformation Format) encoding, etc.) that correspond to thirteen (13) to sixteen (16) numeric digits.

Any suitable technique may be used to identify each string of data within the data 44 (FIG. 1) that includes the appropriate number of consecutive bytes that correspond to thirteen (13) to sixteen (16) numeric digits. One embodiment of such a method includes an “interval scanning” technique, in which a string of data is evaluated in intervals. When such a method is used, bytes of data in periodic sequence (e.g., every thirteenth byte for UTF-8 encoding, two sequential bytes of every twenty-six bytes for UTF-16 encoding, four sequential bytes of every fifty-two bytes for UTF-32 encoding, etc.) are evaluated, while the bytes in between are initially ignored. To enable the search algorithm to identify data of interest across a plurality of formats, or regardless of the particular type of format, in which the data may be encoded (e.g., ASCII/UTF-8, UTF-16LE, UTF-16BE, UTF-32LE, UTF-32BE), a so-called “ordinal” search (e.g., one byte searching for a numeric digit, then two byte searching (both little endian (LE) and big endian (BE)) for a numeric digit, then four byte searching (both LE and BE) for a numeric digit, etc.) may be conducted. For the sake of simplicity, the term “byte,” as used herein, includes a single byte in UTF-8 encoding, an adjacent pair of bytes in UTF-16 encoding, and an adjacent set of four bytes in UTF-32 encoding.

If the value of the byte corresponds to a decimal numeral (i.e., 0, 1, 2, 3, 4, 5, 6, 7, 8, or 9), that byte is identified as a tagged numeric byte, from which a byte-by-byte analysis, or sequential search, may then commence. In the sequential search, bytes adjacent to both “sides” of the tagged numeric byte may be evaluated to determine whether or not they also correspond to decimal numerals. The sequential search may continue until a determination is made that the number of sequential bytes that correspond to decimal numerals is too short (e.g., <13 digits, etc.) or too long (e.g., >16 digits, etc.) to comprise an account number for a credit card or debit card.

Once possible data of interest (e.g., a possible payment card account number, etc.), or a tagged string, has been identified from evaluating the data, in some embodiments, the tagged string that includes possible data of interest may be subjected to further analysis. In some embodiments, further analysis may be conducted immediately after a tagged string of possible data of interest is identified from the data. In other embodiments, further analysis may not occur until after the data has been completely evaluated to identify, or tag, all of the strings therein that may comprise possible data of interest.

Any further analysis of the possible data of interest or of a tagged string including the same (e.g., a data string corresponding to thirteen (13) to sixteen (16) consecutive numeric digits, etc.) may provide an increased confidence that the possible data of interest is actual data of interest with relatively low processing requirements, so data strings that have a lower likelihood of comprising actual data of interest are disregarded, or weeded out, before the process flows to a more intensive final analysis (see, e.g., reference 300 of FIG. 3). These “faster” preliminary evaluation processes, or weed-out processes, are intended to identify any “likely data of interest,” such as a likely payment card account number.

With reference to FIG. 3, at reference 250, an embodiment of a preliminary evaluation process that is referred to herein as a “delimiter search” may be conducted. In a delimiter search, a non-limiting example of which is illustrated by the flow chart of FIG. 4 and the schematic representation of FIG. 4A, a pair of bytes that surrounds a tagged string that comprises possible data of interest may be analyzed.

In a specific embodiment, a byte that immediately precedes a tagged string S_(T) of bytes comprising possible data of interest, which is referred to herein as a “preceding byte B_(P),” may be analyzed at reference 252. Specifically, the value of the preceding byte B_(P) may be identified. Analysis of the preceding byte B_(P) may be conducted in an ordinal fashion (e.g., analysis of one byte, then analysis of two bytes (both little endian (LE) and big endian (BE)), then four byte analysis (both LE and BE), etc.), enabling an evaluation for known delimiters that is not limited to a certain UTF.

At reference 254, the value of the preceding byte B_(P) may be compared with an index of values of characters that are known to be used to identify the limits of a data string, or string of bytes, that corresponds to a particular type of data of interest, such as a payment card account number. Such characters are also referred to herein as “delimiters.” In a specific embodiment, an index of delimiter values may include values that correspond to one or more of a comma (,), a tab ( ), a space ( ), a slash (/ or \), or any other known delimiter.

If the value of the preceding byte Bp does not correspond to the value of a known delimiter, the possible data of interest may be disregarded at reference 256. In embodiments where further analysis follows the identification of a single string of bytes that may comprise data of interest, the process flow may return to reference 210 of FIG. 3, where another tagged string of bytes that comprises possible data of interest may be identified. In embodiments where the further analysis of possible data of interest follows the identification of all possible data of interest within the data, process flow may return to reference 252 of FIG. 4, where the bytes that surround another tagged string may be evaluated.

If, at reference 254, it is determined that the preceding byte Bp has a value that corresponds to the value of a known delimiter, process may flow to reference 258, where a byte that immediately follows a string of bytes comprising possible data of interest, which is referred to herein as a “following byte B_(F),” may be analyzed. Specifically, the value of the following byte B_(F) may be determined. At reference 260, the value of the following byte B_(F) is compared with the index of known delimiters.

If the following byte B_(F) has the same value as a known delimiter, process may flow to reference 262. In some embodiments, the following byte B_(F) must have the same value as the preceding byte B_(P) for process to flow to reference 262. At reference 262, the tagged string and its possible data of interest are identified as a suspected sensitive data string.

Referring again to FIG. 3, one or more additional techniques for further evaluating a tagged string or a suspected sensitive data string may be conducted at reference 270. In the embodiment illustrated by FIG. 3, a tagged string or a suspected sensitive data string may be evaluated, at reference 270, to determine whether it includes a known identifier of sensitive data. The evaluation of a tagged string or a suspected sensitive data string to detect any known identifiers of sensitive data may be effected in any suitable manner. In embodiments where the data is being evaluated to identify potential account numbers for payment cards, the known identifier may comprise a bank identification number (BIN). As known in the art, BINs include four to six consecutive numeric digits, which typically comprise the first digits in an account number.

A BIN search that incorporates teachings of the present invention may include an analysis of a fixed number of bytes that correspond to digits (e.g., four, six, etc.) of (e.g., at the beginning of, at the end of, in the middle of, scattered throughout, etc.) a potential account number for a payment card. These bytes may be analyzed in a so-called “trie” algorithm, in which a first byte is evaluated at a first node of the “trie.” Such an analysis may be conducted in an ordinal fashion (e.g., one byte searching, then two byte searching (both little endian (LE) and big endian (BE)), then four byte searching (both LE and BE), etc.).

If the value of the first byte does not correspond to a first digit that is known to be present in a BIN, the BIN search may be terminated and the string of data is no longer considered to be a potential account number. If, in the alternative, the value of the first byte is equal to, or matches, a first digit of a known BIN, the search proceeds to a second node of the trie that corresponds to the identified value of the first digit (i.e., a database of a group of second digits that are known to follow the identified first digit in a group of known BINs). Again, if the second analyzed byte does not have a value equal to the second digit of any known BIN that also includes the first digit, the search may be terminated and the string of data may no longer be considered to comprise a potential account number. If the value of the second analyzed byte is equal to the second digit of a known BIN, the process continues to a third node of the trie, where the BIN search continues. If, following conclusion of the BIN search, the values of all of the analyzed bytes match the corresponding digits of a known BIN, the potential account number may be subjected to further analysis.

In instances where a further evaluation process is terminated, process may flow to back to FIG. 3. The part of the process of FIG. 3 to which the process returns may depend upon the manner in which data is being evaluated. In embodiments where the evaluation progresses completely in series; i.e., when a tagged string is subjected to further evaluation immediately after the tagged string is identified as including possible data of interest, process may flow back to reference 210 of FIG. 3. At reference 210, the data 44 (FIG. 1) may be searched for more possible data of interest.

In embodiments where further processing is not conducted until all of the data 44 has been evaluated for possible data of interest, and in which all further evaluation of a tagged string is conducted before any further processing is conducted on another tagged string, the evaluation progresses partially in series. When the evaluation progresses partially in series, the process flow may return to reference 250 of FIG. 3, where further evaluation of another tagged string may be initiated.

In embodiments where further evaluation occurs in parallel; i.e., one mode of further evaluation is conducted on all candidates (e.g., tagged strings, suspected sensitive data strings, likely sensitive data strings, etc.) before the next mode of further evaluation conducted on remaining candidates, the process flow may return to reference 270 of FIG. 3.

Returning reference again to FIG. 3, at reference 300, a tagged string that comprises potentially sensitive data of interest may be subjected to verification. In some embodiments, known processes may be used to determine the likelihood that a string of decimal numerals is an account number for a credit card or debit card. In a specific embodiment, a known validation or “checksum” algorithm, such as the Luhn algorithm, may be used to determine whether or not a potential account number is an actual account number.

Once the evaluation of one data string (e.g., the tagged string, etc.) at reference 300 is complete, the process flow may return to another location on FIG. 3. The location to which the process flow returns (e.g., reference 210, 250, 270, or 300) depends, of course, upon whether the evaluation progresses completely in series, partially in series, or in parallel.

While the above-described systems and processes have been described in terms of searches for potential credit card or debit card account numbers, they are also applicable to searches for other sensitive types of information, including bank account numbers, Social Security numbers, drivers license numbers, and the like.

Although the foregoing description contains many specifics, these should not be construed as limiting the scope of the invention or of any of the appended claims, but merely as providing information pertinent to some specific embodiments that may fall within the scopes of the invention and the appended claims. Features from different embodiments may be employed in combination. In addition, other embodiments of the invention may also be devised which lie within the scopes of the invention and the appended claims. The scope of the invention is, therefore, indicated and limited only by the appended claims and their legal equivalents. All additions, deletions and modifications to the invention, as disclosed herein, that fall within the meaning and scopes of the claims are to be embraced by the claims. 

What is claimed:
 1. A system for identifying potentially sensitive information, comprising: a scanning device configured to communicate with a memory device that stores data including potentially sensitive information, the scanning device programmed to: identify a string of sequential bytes of at least one predetermined length in which each byte has a value corresponding to a decimal number; evaluate a preceding byte immediately preceding the string of sequential bytes to determine whether the preceding byte has a value that corresponds to a known delimiter; evaluate a following byte immediately following the string of sequential bytes to determine whether the following byte has a value that corresponds to a known delimiter; identify each string immediately preceded by a preceding byte with a value corresponding to a known delimiter and immediately followed by a following byte with a value corresponding to a known delimiter as a suspected sensitive data string.
 2. The system of claim 1, wherein the scanning device is programmed to identify each string immediately preceded by a preceding byte with a value corresponding to a known delimiter and immediately followed by a following byte with a value corresponding to a known delimiter as the suspected sensitive data string when the value of the preceding byte and the value of the following byte correspond to a same known delimiter.
 3. The system of claim 1, wherein the at least one predetermined length of the string of sequential bytes corresponds to a length of sensitive information of interest.
 4. The system of claim 3, wherein the at least one predetermined length of the string of sequential bytes is about four bytes to about sixteen bytes.
 5. The system of claim 4, wherein the at least one predetermined length of the string of sequential bytes is about thirteen bytes to about sixteen bytes.
 6. The system of claim 1, wherein the scanning device is also programmed to: intermittently scan the data to identify a data string of sequential bytes that correspond to decimal numerals, the data string having a length that corresponds to the at least one predetermined length.
 7. The system of claim 6, wherein the scanning device is programmed to evaluate each n-th byte of at least a portion of the data, with n corresponding to the at least one predetermined length.
 8. The system of claim 7, wherein the scanning device is also programmed to: evaluate whether bytes of a substring of the suspected sensitive data string collectively correspond to a known identifier of sensitive data.
 9. The system of claim 8, wherein the scanning device is also programmed to: compare the suspected sensitive data string to a trie to determine a likelihood that the suspected sensitive data string comprises an actual sensitive data string.
 10. The system of claim 1, wherein the scanning device is also programmed to: evaluate whether bytes of a substring of the suspected sensitive data string collectively correspond to a known identifier of sensitive data.
 11. The system of claim 1, wherein the scanning device is also programmed to: compare the suspected sensitive data string to a trie to determine a likelihood that the suspected sensitive data string comprises an actual sensitive data string.
 12. A system for identifying potentially sensitive information, comprising: a memory device in which data including potentially sensitive information is stored; and a scanning device in communication with the memory device, the scanning device programmed to: identify a string of sequential bytes of at least one predetermined length in which each byte has a value corresponding to a decimal number; evaluate a preceding byte immediately preceding the string of sequential bytes to determine whether the preceding has a value that corresponds to a known delimiter; evaluate a following byte immediately following the string of sequential bytes to determine whether the following byte has a value that corresponds to a known delimiter; identify each string immediately preceded by a preceding byte with a value corresponding to a known delimiter and immediately followed by a following byte with a value corresponding to a known delimiter as a suspected sensitive data string.
 13. The system of claim 12, further comprising: an administrator that commissions scanning of the memory device.
 14. The system of claim 13, wherein the scanning device is also programmed to: report the suspected sensitive data string to the administrator.
 15. The system of claim 12, wherein the scanning device is also programmed to: intermittently scan the data to identify a data string of sequential bytes that correspond to decimal numerals, the data string having a length that corresponds to the at least one predetermined length.
 16. The system of claim 15, wherein the scanning device is programmed to evaluate each n-th byte of at least a portion of the data, with n corresponding to the at least one predetermined length.
 17. The system of claim 12, wherein the scanning device is also programmed to: evaluate whether bytes of a substring of the suspected sensitive data string collectively correspond to a known identifier of sensitive data.
 18. The system of claim 17, wherein the known identifier of sensitive data comprises a bank identification number.
 19. The system of claim 12, wherein the scanning device is also programmed to: compare the suspected sensitive data string to a trie to determine a likelihood that the suspected sensitive data string comprises an actual sensitive data string.
 20. A system for identifying potential payment card numbers, comprising: a scanning device for evaluating data stored by a memory device under control of a merchant, the data including potential payment card numbers, the scanning device programmed to: identify a string of sequential bytes of about thirteen bytes to about sixteen bytes in which each byte has a value corresponding to a decimal number; evaluate a preceding byte immediately preceding the string of sequential bytes to determine whether the preceding byte has a value that corresponds to a known delimiter; evaluate a following byte immediately following the string of sequential bytes to determine whether the following byte has a value that corresponds to a known delimiter; identify each string immediately preceded by a preceding byte with a value corresponding to a known delimiter and immediately followed by a following byte with a value corresponding to a known delimiter as a suspected payment card number.
 21. The system of claim 20, wherein the known delimiter includes at least one of a space, a tab, a comma, a forward slash and a backslash.
 22. The system of claim 20, wherein the scanning device is programmed to identify a string of sequential bytes of about thirteen bytes to about sixteen bytes in which each byte has a value corresponding to a decimal number by: evaluating every thirteenth byte of the data; tagging each thirteenth byte that corresponds to a decimal number to provide a tagged byte; enumerating the tagged byte; sequentially evaluating and enumerating bytes preceding and following each tagged byte until a value of a preceding sequentially evaluated byte and a value of a following sequentially evaluated byte does not correspond to a decimal number; and determining whether a number of sequential enumerated bytes is between thirteen and sixteen bytes, inclusive.
 23. The system of claim 20, wherein the scanning device is also programmed to: evaluate whether a group of bytes of the suspected payment card number collectively corresponds to a known bank identification number.
 24. The system of claim 23, wherein the group of bytes of the suspected payment card number comprises a first four bytes, a first five bytes, or a first six bytes of the suspected payment card number.
 25. The system of claim 20, wherein the scanning device is also programmed to: compare the suspected payment card number to a trie to determine a likelihood that the suspected payment card number comprises an actual payment card number.
 26. The system of claim 20, further comprising: the merchant; and the memory device.
 27. The system of claim 26, further comprising: an administrator that sets a data security standard and commissions scanning of the memory device to determine the merchant's compliance with the data security standard.
 28. The system of claim 27, wherein the administrator comprises at least one of an acquirer and an issuer.
 29. The system of claim 27, further comprising: a compliance monitor that operates the scanning device when commissioned by the administrator. 